Chapter 26 — Role Roadmap: How Different Roles Go Deeper With WorkBuddy
Role application shouldn't start from "what prompts does this role have"; it should start from three questions: which work repeats, which deliverables have stable standards, and which decisions must be human-owned.
Four Maturity Levels of Role Application
| Level | How it works | Typical form | Condition to move up |
|---|---|---|---|
| L1 One-off assist | Human gives full material; AI generates draft | Minutes, summaries, tables, PPT | Output acceptable; 3 consecutive successes |
| L2 Fixed template | Uses task cards and standard output | Weekly report, review, client brief | Input fields and acceptance rules stable |
| L3 Workflow | Skill, knowledge base, connector collaboration | Content flow, knowledge flow, report flow | Has an owner, logs and exception handling |
| L4 Team capability | Projects, expert teams and automated running | Department-level digital employee | Permissions, cost and asset governance in place |
Every role should start from low-risk L1 tasks. Not every task needs to reach L4; low-frequency, high-variance or high-responsibility work is better kept as "AI assist + human decision".
Product Manager
| Scene | Input | Deliverable |
|---|---|---|
| User-interview organizing | Audio transcript, interview guide | Pain points, quotes, questions to verify |
| Feedback clustering & version review | Tickets, comments, analytics summaries | Problem categories, impact scope, evidence table |
| Competitor evidence base | Official site, pricing, changelog, reviews | Traceable comparison table and periodic brief |
| Product-discovery workflow | Feedback, data, competitors, business goals | Opportunity map and decision material |
Operations & Marketing
| Scene | Input | Deliverable |
|---|---|---|
| Content rewriting, asset inventory | Approved long article, image directory | Platform drafts, asset list |
| Title, cover & platform adaptation | Approved fact pack, brand spec | Title pool, WeChat cover, Xiaohongshu long image, voiceover script |
| Topic & content middle-platform | News sources, comments, brand spec, history | Candidate pool, evidence table, content calendar, review library |
| Content expert team | Hotspots, product material, channel data | Research, script, storyboard, multi-platform drafts, review |
Sales & Pre-sales
| Scene | Deliverable | Risk point |
|---|---|---|
| Post-meeting minutes | Needs, objections, todos, owners | Writing speculation as client commitment |
| Client research | Profile, public activity, opportunity hypotheses | Using stale or same-name company material |
| Proposal & demo | Proposal outline, demo script, FAQ | Fabricating capability, price and cases |
| Follow-up workflow | CRM draft, reminders, material updates | Unconfirmed writes and sends |
HR & Administration
| Scene | Recommended做法 | Must control |
|---|---|---|
| Policy summary, material check | Generate FAQ from approved docs | Version date and applicable scope |
| Onboarding & training | Generate learning paths, decks, checklists | Employee-data minimization |
| HR knowledge assistant | Connect policy library to answer common questions | Permissions, citations and human escalation |
| HR-process assist | Reminders, material completeness, reports | No automated hiring decisions |
Finance & Legal
| Finance scene | Legal scene | Human gate |
|---|---|---|
| Invoice recognition, bill tidying | Clause extraction, version comparison | Amount and source-text review |
| Budget variance, anomaly list | Standard-clause deviation list | Scope and risk judgment |
| Month-close material pipeline | Contract knowledge base, review workbench | Professional sign-off |
| Controlled system write-back | Contract-flow reminders | Payment, filing, signing confirmation |
R&D & IT
| Scene | Deliverable | Checkpoint |
|---|---|---|
| Code understanding, tech docs | Architecture diagram, README, module list | Consistent with actual code |
| Testing & defect analysis | Test matrix, repro steps, fix suggestions | Tests pass, code review |
| Dev workflow | Branch changes, CI diagnosis, release notes | Merge and deploy confirmation |
| IT automation | Inspection, alert summary, knowledge base | Production permissions and incident response |
Department Rollout Template
Each role first picks one scene and fills this card:
| Item | Content |
|---|---|
| Original flow | Who, when, which systems, how long |
| Input | Files, fields, permissions, quality issues |
| Output | Files, system records, notification recipients |
| Acceptance | Accuracy, completeness, timeliness and risk |
| Human gate | Who confirms, when to pause |
| Metrics | Baseline, target, observation period |
| Owner | Business, tech, asset maintainer |
The end of role rollout isn't "everyone knows how to ask AI", but forming a batch of standard workflows that new people can reuse, that owners maintain, and that are traceable when something goes wrong.